Method and terminal device for data transmission

ABSTRACT

Embodiments of the present application disclose a method and terminal device for data transmission. The method is applied to a vehicle-to-everything system, and comprises: a terminal device in a first protocol layer determining, according to service information of data to be sent, a transmission mechanism for transmitting the data to be sent. The method and terminal device in the embodiments of the present application enhance data transmission capabilities.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.16/996,766 filed Aug. 18, 2020, which is a continuation of PCTApplication No. PCT/CN2018/085860, filed on May 7, 2018 and entitled“Method and Terminal Device For Data Transmission”, which claimspriority to PCT Application No. PCT/CN2018/081182, filed on Mar. 29,2018 and entitled “Method and Terminal Device For Data Transmission”.The disclosures of the above applications are hereby incorporated byreference in their entireties.

TECHNICAL FIELD

Embodiments of the disclosure relate to the field of communication, andmore particularly to a method for data transmission and terminal device.

BACKGROUND

Internet of vehicles or Vehicle to Everything (V2X) communication systemis a sidelink (SL) transmission technology based on device-to-device(D2D) communication. Unlike a conventional long term evolution (LTE)system in which data reception and sending is performed through a basestation, an Internet of vehicles system adopts a D2D communicationmanner and thus is higher in spectrum efficiency and lower intransmission delay.

Along with the evolution of communication systems, more and moretransmission mechanisms have been adopted for data channels, forexample, a digital modulation mechanism, a rate matching mechanism, aduplicate transmission mechanism or a Transmit Diversity (TxD). Thedigital modulation mechanism may include quadrature phase shiftingkeying (QPSK), 16 Quadrature Amplitude Modulation (QAM), 64QAM and thelike. How to determine a transmission mechanism to be adopted by aterminal device to send data is a problem to be solved.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of an application scenario according to anembodiment of the disclosure.

FIG. 2 is a schematic diagram of another application scenario accordingto an embodiment of the disclosure.

FIG. 3 is a schematic block diagram of a method for sending dataaccording to an embodiment of the disclosure.

FIG. 4 is a schematic block diagram of another method for sending dataaccording to an embodiment of the disclosure.

FIG. 5 is a schematic block diagram of a terminal device according to anembodiment of the disclosure.

FIG. 6 is another schematic block diagram of a terminal device accordingto an embodiment of the disclosure.

FIG. 7 is another schematic block diagram of a terminal device accordingto an embodiment of the disclosure.

FIG. 8 is another schematic block diagram of a terminal device accordingto an embodiment of the disclosure.

FIG. 9 is a schematic block diagram of another method for sending dataaccording to an embodiment of the disclosure.

FIG. 10 is another schematic block diagram of a terminal deviceaccording to an embodiment of the disclosure.

FIG. 11 is another schematic block diagram of a terminal deviceaccording to an embodiment of the disclosure.

FIG. 12 is a schematic block diagram of a chip according to anembodiment of the disclosure.

FIG. 13 is another schematic block diagram of a chip according to anembodiment of the disclosure.

FIG. 14 is another schematic block diagram of a chip according to anembodiment of the disclosure.

DETAILED DESCRIPTION

The technical solutions in the embodiments of the disclosure will beclearly and completely described below in combination with the drawingsin the embodiments of the disclosure.

It is to be understood that the technical solutions of the embodimentsof the disclosure may be applied to various communication systems, forexample, a Global System of Mobile communication (GSM), a Code DivisionMultiple Access (CDMA) system, a Wideband Code Division Multiple Access(WCDMA) system, a General Packet Radio Service (GPRS), an LTE system, anLTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex(TDD), a Universal Mobile Telecommunication System (UMTS), a WorldwideInteroperability for Microwave Access (WiMAX) communication system, NRor a future 5th-Generation (5G) system.

Particularly, the technical solutions of the embodiments of thedisclosure may be applied to various nonorthogonal multiple accesstechnology-based communication systems, for example, a Sparse CodeMultiple Access (SCMA) system and a Low Density Signature (LDS) system,and of course, the SCMA system and the LDS system may also have othernames in the field of communication. Furthermore, the technicalsolutions of the embodiments of the disclosure may be applied tomulti-carrier transmission systems adopting nonorthogonal multipleaccess technologies, for example, Orthogonal Frequency DivisionMultiplexing (OFDM), Filter Bank Multi-Carrier (FBMC), GeneralizedFrequency Division Multiplexing (GFDM) and Filtered-OFDM (F-OFDM)systems adopting the nonorthogonal multiple access technologies.

In the embodiments of the disclosure, a terminal device may refer toUser Equipment (UE), an access terminal, a user unit, a user station, amobile station, a mobile radio station, a remote station, a remoteterminal, a mobile device, a user terminal, a terminal, a wirelesscommunication device, a user agent or a user device. The access terminalmay be a cell phone, a cordless phone, a Session Initiation Protocol(SIP) phone, a Wireless Local Loop (WLL) station, a Personal DigitalAssistant (PDA), a handheld device with a wireless communicationfunction, a computing device or another processing device connected to awireless modem, a vehicle device, a wearable device, a terminal devicein a future 5G network, a terminal device in a future evolved PublicLand Mobile Network (PLMN) or the like. There are no limits made in theembodiments of the disclosure.

In the embodiments of the disclosure, a network device may be a deviceconfigured to communicate with the terminal device. The network devicemay be a Base Transceiver Station (BTS) in the GSM or the CDMA, may alsobe a NodeB (NB) in the WCDMA system, may also be an Evolutional Node B(eNB or eNodeB) in the LTE system and may further be a wirelesscontroller in a Cloud Radio Access Network (CRAN) scenario. Or thenetwork device may be a relay station, an access point, a vehicledevice, a wearable device, a network device in the future 5G network, anetwork device in the future evolved PLMN or the like. There are nolimits made in the embodiments of the disclosure.

In view of this, the embodiments of the disclosure provide a method fordata transmission and a terminal device. A transmission mechanism to beadopted is determined according to service information of data to besent, and then a terminal device may send the data by use of a moresuitable transmission mechanism, so that data transmission performanceis improved.

A first aspect provides a method for data transmission, which may beapplied to an Internet of vehicles system and include: determining at afirst protocol layer, by a terminal device, a transmission mechanism fortransmitting data to be sent, according to service information of thedata to be sent.

In a possible implementation mode, the service information may includeat least one piece of information of the following information: aservice identifier, an Internet Protocol (IP) address, a service type, aservice requirement, band information, version information, a fullyqualified domain name (FQDN), layer-2 address information,proximity-based service (ProSe) per-packet priority (PPPP) information,or ProSe per-packet reliability (PPPR) information.

Alternatively, the IP address may be an IP address of a server.

In a possible implementation mode, the method may further include:acquiring at a second protocol layer, by the terminal device, theservice information; and sending at the second protocol layer, by theterminal device, the service information to the first protocol layer.

In a possible implementation mode, when the service information isversion information, acquiring at the second protocol layer, by theterminal device, the service information of the data to be sent mayinclude: determining at the second protocol layer, by the terminaldevice, the version information of the data to be sent according to atleast one piece of information of the following information: a serviceidentifier, an IP address, a service type, a service requirement, bandinformation, a FQDN, layer-2 address information, PPPP information, orPPPR information, wherein the version information is used for indicatinga protocol version for a service corresponding to the data to be sent.

In a possible implementation mode, when the service information is atleast one piece of information of the following information: a serviceidentifier, an IP address, a service type, a service requirement, bandinformation, a FQDN, layer-2 address information, PPPP information, orPPPR information, the method may further include: determining at thefirst protocol layer, by the terminal device, version information of thedata to be sent according to the at least one piece of information,wherein the version information is used for indicating a protocolversion for a service corresponding to the data to be sent.

In a possible implementation mode, the operation of determining, by theterminal device, the version information of the data to be sentaccording to the at least one piece of information may include:determining, by the terminal device, the version information of the datato be sent, according to the at least one piece of information and amapping relationship between the at least one piece of information andthe version information.

In a possible implementation mode, the mapping relationship may bepre-stored in the terminal device, or may be configured by a networkdevice, or may be configured by a server.

In a possible implementation mode, the transmission mechanism mayinclude at least one of the following: a digital modulation mechanism, arate matching mechanism, a duplicate transmission mechanism, or aTransmit Diversity (TxD).

In a possible implementation mode, the digital modulation mechanism mayinclude one of binary phase shifting keying (BPSK), QPSK, 16QAM, 64QAMand 256QAM.

In a possible implementation mode, the first protocol layer may be anaccess layer, and the second protocol layer may be an application layer.

In a possible implementation mode, the method may further include that:the terminal device determines, at the first protocol layer, atransmission carrier for the data to be sent, according to a mappingrelationship between the transmission mechanism and a transmissioncarrier.

In a possible implementation mode, the operation of determining at thefirst protocol layer, by the terminal device, the transmission mechanismfor transmitting the data to be sent according to the serviceinformation of the data to be sent may include: determining at the firstprotocol layer, by the terminal device, at least one transmissionmechanism for transmitting the data to be sent, according to the serviceinformation; and the method may further include: determining at thefirst protocol layer, by the terminal device, a transmission mechanismfor transmission of the data to be sent, from the at least onetransmission mechanism, according to a mapping relationship between theat least one transmission mechanism and a transmission carrier, and thetransmission carrier for the data to be sent.

In a possible implementation mode, the method may further include:determining at a third protocol layer, by the terminal device, atransmission carrier for the data to be sent, according to a mappingrelationship between the transmission mechanism and the transmissioncarrier, the third protocol layer being a layer below the first protocollayer.

In a possible implementation mode, the operation of determining at thefirst protocol layer, by the terminal device, the transmission mechanismfor transmitting the data to be sent according to the serviceinformation of the data to be sent may include: determining at the firstprotocol layer, by the terminal device, at least one transmissionmechanism for transmitting the data to be sent, according to the serviceinformation; and the method may further include: determining at a thirdprotocol layer, by the terminal device, the transmission mechanism fortransmission of the data to be sent, from the at least one transmissionmechanism, according to a mapping relationship between the at least onetransmission mechanism and a transmission carrier, and the transmissioncarrier for the data to be sent, the third protocol layer being a layerbelow the first protocol layer.

A second aspect provides a method for data transmission, which may beapplied to an Internet of vehicles system and include: acquiring, by aterminal device, service information of data to be sent; anddetermining, by the terminal device, a transmission path fortransmitting the data to be sent, from multiple transmission paths,according to the service information.

In a possible implementation mode, the multiple transmission paths mayinclude a cellular path and at least one SL path, the SL path being aD2D path between two terminal devices.

In a possible implementation mode, the multiple transmission paths mayinclude multiple SL paths, the SL path being a D2D path between twoterminal devices.

In a possible implementation mode, the multiple SL paths may include atleast two of a new radio (NR) link, an LTE link, or a wireless localarea network (WLAN) link.

In a possible implementation mode, the service information may includeat least one piece of information of the following information: aservice identifier, an IP address, a service type, a servicerequirement, band information, version information, an FQDN, layer-2address information, PPPP information, or PPPR information.

In a possible implementation mode, the operation determining, by theterminal device, the transmission path for transmitting the data to besent, from the multiple transmission paths, according to the serviceinformation may include: determining at a first protocol layer, by theterminal device, the transmission path for transmitting the data to besent, from the multiple transmission paths, according to the serviceinformation and path configuration information, wherein the pathconfiguration information is used for indicating a mapping relationshipbetween the service information and a transmission path.

In a possible implementation mode, at least one of the serviceinformation or the path configuration information is configured orpre-stored at the first protocol layer through a network.

In a possible implementation mode, the method may further include:transmitting at the first protocol layer, by the terminal device, thedata to be sent to a protocol layer of the transmission path determinedby the terminal device.

In a possible implementation mode, the first protocol layer may be anapplication layer, an access layer, or a sublayer of the access layer.

A third aspect provides a terminal device, which is configured toexecute the method in the first aspect or any possible implementationmode of the first aspect. Specifically, the terminal device includesunits configured to execute the method in the first aspect or anypossible implementation mode of the first aspect.

A fourth aspect provides a terminal device, which is configured toexecute the method in the second aspect or any possible implementationmode of the second aspect. Specifically, the terminal device includesunits configured to execute the method in the second aspect or anypossible implementation mode of the second aspect.

A fifth aspect provides a terminal device, which includes a memory, aprocessor, an input interface and an output interface. The memory, theprocessor, the input interface and the output interface are connectedthrough a bus system. The memory is configured to store instructions.The processor is configured to execute the instructions stored in thememory to execute the method in the first aspect or any possibleimplementation mode of the first aspect.

A sixth aspect provides a terminal device, which includes a memory, aprocessor, an input interface and an output interface. The memory, theprocessor, the input interface and the output interface are connectedthrough a bus system. The memory is configured to store instructions.The processor is configured to execute the instructions stored in thememory to execute the method in the second aspect or any possibleimplementation mode of the second aspect.

A seventh aspect provides a method for data transmission, which may beapplied to an Internet of vehicles system and include at least one ofthe following: determining, by a terminal device, a transmissionmechanism for transmitting data to be sent on a first transmissionresource, according to configuration information; or selecting, by theterminal device, a transmission resource for the data to be sent,according to the configuration information.

In a possible implementation mode, the configuration information may beused for indicating at least one selectable transmission mechanism onthe first transmission resource.

In a possible implementation mode, the method may further include that:the terminal device receives first indication information, the firstindication information being used for indicating a first transmissionmechanism in the at least one transmission mechanism; and the operationthat the terminal device determines the transmission mechanism fortransmitting the data to be sent on the first transmission resourceaccording to the configuration information may include that: theterminal device determines the first transmission mechanism to be thetransmission mechanism for transmitting the data to be sent on the firsttransmission resource according to the configuration information and thefirst indication information.

In a possible implementation mode, the configuration information may beused for indicating a mapping relationship between the transmissionresource and the transmission mechanism.

In a possible implementation mode, the method may further include:receiving, by the terminal device, second indication information, thesecond indication information being used for indicating a secondtransmission mechanism in the mapping relationship; and the operation ofselecting, by the terminal device, the transmission resource for thedata to be sent according to the configuration information may include:determining, by the terminal device, a transmission resourcecorresponding to the second transmission mechanism in the mappingrelationship, to be the transmission resource for the data to be sent.

In a possible implementation mode, selection of the transmissionresource may include at least one of carrier selection or carrierreselection.

In a possible implementation mode, selection of the transmissionresource may include at least one of resource pool selection or resourcepool reselection.

An eighth aspect provides a terminal device, which is configured toexecute the method in the seventh aspect or any possible implementationmode of the seventh aspect. Specifically, the terminal device includesunits configured to execute the method in the seventh aspect or anypossible implementation mode of the seventh aspect.

A ninth aspect provides a terminal device, which includes a memory, aprocessor, an input interface and an output interface. The memory, theprocessor, the input interface and the output interface are connectedthrough a bus system. The memory is configured to store instructions.The processor is configured to execute the instructions stored in thememory to execute the method in the seventh aspect or any possibleimplementation mode of the seventh aspect.

A tenth aspect provides a chip, which is configured to implement themethod in the first aspect or any possible implementation mode of thefirst aspect, or the method in the second aspect or any possibleimplementation mode of the second aspect or the method in the seventhaspect or any possible implementation mode of the seventh aspect.

Specifically, the chip includes a processor, configured to call and runa computer program in a memory to enable a device installed with thechip to execute the method in the first aspect or any possibleimplementation mode of the first aspect, or the method in the secondaspect or any possible implementation mode of the second aspect or themethod in the seventh aspect or any possible implementation mode of theseventh aspect.

An eleventh aspect provides a computer storage medium, which isconfigured to store computer software instructions for executing themethod in the first aspect or any possible implementation mode of thefirst aspect, or the method in the second aspect or any possibleimplementation mode of the second aspect or the method in the seventhaspect or any possible implementation mode of the seventh aspect, theinstructions including a program designed to execute the aspects.

A twelfth aspect provides a computer program product includinginstructions, which runs in a computer to enable the computer to executethe method in the first aspect or any optional implementation mode ofthe first aspect, or the method in the second aspect or any optionalimplementation mode of the second aspect or the method in the seventhaspect or any possible implementation mode of the seventh aspect.

These aspects or other aspects of the disclosure will become clearer andeasier to understand through the following descriptions about theembodiments.

Each of FIG. 1 and FIG. 2 is a schematic diagram of an applicationscenario according to an embodiment of the disclosure. A network deviceand two terminal devices are exemplarily illustrated in FIG. 1.Alternatively, a wireless communication system may include multiplenetwork devices, and another number of terminal devices may be includedin coverage of each network device. There are no limits made thereto inthe embodiments of the disclosure. In addition, the wirelesscommunication system may further include another network entity such asa Mobile Management Entity (MME), a Serving Gateway (S-GW) and a Packetdata Network Gateway (P-GW). However, the embodiments of the disclosureare not limited thereto.

Specifically, a terminal device 20 may communicate with a terminaldevice 30 in a D2D communication mode. During D2D communication, theterminal device 20 directly communicates with the terminal device 30through a D2D link, i.e., an SL. For example, as illustrated in FIG. 1or FIG. 2, the terminal device 20 directly communicates with theterminal device 30 through the SL. In FIG. 1, the terminal device 20communicates with the terminal device 30 through the SL, for which atransmission resource is allocated by a network device. In FIG. 2, theterminal device 20 communicates with the terminal device 30 through theSL, for which a transmission resource is selected independently by theterminal device, and does not have to be allocated by the networkdevice.

The D2D communication mode may be applied to Vehicle to Vehicle (V2V)communication or V2X communication. In V2X communication, X maygenerally refer to any device with a wireless receiving and sendingcapability, for example, but not limited to, a wireless device moving ata low speed, a vehicle device moving at a high speed or a networkcontrol node with a wireless transmitting and receiving capability, etc.It is to be understood that the embodiments of the disclosure are mainlyapplied to a V2X communication scenario but may also be applied to anyother D2D communication scenario. There are no limits made thereto inthe embodiments of the disclosure.

In an Internet of vehicles system, two types of terminal devices mayexist, i.e., terminal devices having a sensing capability, for example,Vehicle User Equipment (VUE) or Pedestrian User Equipment (PUE), andterminal devices having no sensing capability, for example, PUE. VUE hasa higher processing capability, and is usually powered by a storagebattery in a vehicle. PUE has a relatively low processing capability,and thus reduction in power consumption is also a main factor to beconsidered for PUE. Therefore, in an existing Internet of vehiclessystem, VUE is considered to have a complete receiving capability andsensing capability, while PUE is considered to have partial or noreceiving and sensing capabilities. If the PUE has the partial sensingcapability, the PUE may adopt a sensing method similar to that for theVUE for resource selection, and select an available resource fromresources that can be sensed. If the PUE has no sensing capability, thePUE randomly selects a transmission resource from a resource pool.

In 3rd Generation Partnership Project (3GPP) Release-14, twotransmission modes are defined, i.e., a transmission mode 3 (mode 3) anda transmission mode 4 (mode 4). In the transmission mode 3, atransmission resource of a terminal device is allocated by a basestation, and the terminal device performs data transmission on an SLaccording to the resource allocated by the base station; and the basestation may allocate a resource for single transmission to the terminaldevice, or may allocate a resource for semi-persistent transmission tothe terminal device. In the transmission mode 4, if a terminal devicehaving a sensing capability, the terminal device transmits data in amanner combining sensing and reservation;, and if the terminal devicehas no sensing capability, the terminal device randomly selects atransmission resource from a resource pool. The terminal device havingthe sensing capability acquires an available transmission resource setfrom the resource pool in a sensing manner, and the terminal devicerandomly selects a resource from the set for data transmission. Since aservice in an Internet of vehicles system is periodic, the terminaldevice usually adopts a semi-persistent transmission manner, namely theterminal device, after selecting a transmission resource, may keep usingthe resource in multiple transmission cycles, so that probabilities ofresource reselection and resource conflict are reduced. The terminaldevice may carrying information for reserving the resource for nexttransmission in control information for the current transmission, suchthat other terminal device(s) can detect the control information of theterminal device, thereby determining whether the resource is reservedand used by the terminal device. In this way, resource conflict isreduced.

Along with the evolution of communication systems, more and moretransmission mechanisms have been adopted for data channels, forexample, a digital modulation mechanism, a rate matching mechanism, aduplicate transmission mechanism or a TxD. The digital modulationmechanism may include QPSK, 16QAM, 64QAM and the like. How to determinea transmission mechanism to be adopted by a terminal device to send datais a problem to be solved.

It is to be understood that the embodiments of the disclosure aredescribed with the Internet of vehicles system as an example. Theembodiment of the disclosure may also be applied to, for example, datatransmission between a terminal device and a network device, in acellular network. The embodiments of the disclosure should not belimited thereto.

FIG. 3 is a schematic block diagram of a method 100 for datatransmission according to an embodiment of the disclosure. Asillustrated in FIG. 3, the method 100 is applied to an Internet ofvehicles system. The method 100 includes part or all of the followingcontents.

In S110, a terminal device determines, at a first protocol layer, atransmission mechanism for transmitting data to be sent according toservice information of the data to be sent.

First of all, it is necessary to describe the terminal device in theInternet of vehicles system. The terminal device in the Internet ofvehicles may generally include a context awareness layer, a networkaccess layer, a network control layer and an application/service layer.Each layer forms a corresponding relationship with a control device at anetwork side.

In the embodiment of the disclosure, the terminal device may acquire, ata second protocol layer, the service information of the data to be sentat first. For example, the terminal device may acquire the serviceinformation of the data to be sent from the application/service layer.The service information may be any information related to a serviceassociated with the data to be sent. For example, it may be at least oneof a service identifier, an IP address, a service type, a servicerequirement, band information, version information, an FQDN, layer-2address information, PPPP information, or PPPR information. The terminaldevice may send, at the second protocol layer, the acquired serviceinformation of the data to be sent to the first protocol layer, and theterminal device may further determine, at the first protocol layer, thetransmission mechanism for transmitting the data to be sent according tothe service information acquired at the second protocol layer. Forexample, the terminal device may determine, at the access layer, thetransmission mechanism for transmitting the data to be sent according tothe service information acquired at the application layer. After thetransmission mechanism is determined, the terminal device may adopt thetransmission mechanism to send the data.

Or, the terminal device may also acquire, at the first protocol layer,the service information of the data to be sent, and determine, at thesecond protocol layer, the transmission mechanism for transmitting thedata to be sent, according to the acquired service information. Forexample, the terminal device may acquire, at the application layer, theservice information of the data to be sent, and determine, at theapplication layer, the transmission mechanism for transmitting the datato be sent, according to the service information.

Alternatively, a network device or a server may configure a mappingrelationship between different service information and differenttransmission mechanisms in advance. Or, the mapping relationship may bepre-stored in the terminal device. Taking service type and digitalmodulation mechanism as an example, there is made such a hypothesis thata voice service may correspond to BPSK, QPSK and 16QAM and a videoservice may correspond to 16QAM, 64QAM and 256QAM, if the terminaldevice determines that a service type of the data to be sent is a voiceservice, the transmission mechanism available for the terminal devicemay be one of BPSK, QPSK and 16QAM. If the terminal device determinesthat the service type of the data to be sent is a video service, thetransmission mechanism available for the terminal device may be one of16QAM, 64QAM and 256QAM.

Alternatively, the network device may not configure the mappingrelationship between the service information and the transmissionmechanisms in advance; instead, after the terminal device sends theservice information of the data to be sent, one transmission mechanismmay be directly selected from multiple transmission mechanisms totransmit the data. For example, service type and digital modulationmechanism are still adopted. If the terminal device determines that theservice type of the data to be sent is a voice service, the terminaldevice may select one transmission mechanism from all digital modulationmechanisms such as BPSK, 2/π-BPSK, QPSK, 16QAM, 64QAM and 256QAM. If theterminal device determines that the service type of the data to be sentis a video service, the terminal device may also select one transmissionmechanism from all the digital modulation mechanisms. The transmissionmechanism selected for the voice service and the transmission mechanismselected for the video service may be the same or may be different fromeach other.

It is to be understood that descriptions are made here only with thecondition that the transmission mechanism is the digital modulationmechanism as an example. Of course, the transmission mechanism may alsobe a rate matching mechanism, duplicate transmission mechanism and thelike listed above.

Part of the service information listed above will be described below oneby one.

The service identifier refers to information for identifying theservice. Different services may correspond to different identifiers. Itis similar to other identification information and will not be describedin details herein.

The IP address may refer to a serial number assigned to the terminaldevice in a network. The IP address may be a 32 bit binary number, forexample, 43.246.231.110. The IP address may be an IP address of aserver.

The service type is the abovementioned service type. For example, theservice type may be a video service, a voice service or a shortmessaging service.

The service requirement may refer to delay requirements, raterequirements, reliability requirements and the like of differentservices. For example, an Ultra-reliable and Low Latency Communications(URLLC) service in 5G has a relatively high delay requirement, while anEnhanced Mobile Broadband (EMBB) in 5G has a relatively low delayrequirement.

The band information may refer to information of band(s) in which theservice is sent. Different services may be sent on different bands.

FQDN information may refer to a host name plus a full path, and alldomain members in a sequence are listed in the full path.

The layer-2 address information: layer 2 may refer to a data link layerand, for example, may refer to a Media Access Control (MAC) layer, aRadio Link Control (RLC) layer and Packet Data Convergence Protocol(PDCP).

The version information: the version information may refer to a protocolversion for the service, for example, Rel-14 and Rel-15. For example, inthe Internet of vehicles system, some new services such as an autopilotservice and a vehicle formation service are introduced into Rel-15,compared with Rel-14.

Alternatively, in the embodiment of the disclosure, if the serviceinformation is the version information, the terminal device determines,at the second protocol layer, the version information of the data to besent according to at least one of the following information: the serviceidentifier, the IP address, the service type, the service requirement,the band information, the FQDN, the layer-2 address information, thePPPP information, or the PPPR information, the version information beingused for indicating a protocol version for a service corresponding tothe data to be sent.

Furthermore, the terminal device may send, at the second protocol layer,the determined version information to the first protocol layer.

Specifically, the terminal device may determine, at the second protocollayer, the version, for example, Rel-14, Rel-15 or another protocolversion, for the service corresponding to the data to be sent at firstaccording to the service information except the version information, theterminal device may further send, at the second protocol layer, versionindication information to the first protocol layer, different versionscorresponding to different transmission mechanisms, and then theterminal device may determine, at the first protocol layer, thetransmission mechanism corresponding to the version indicated by theversion indication information. For example, if the second protocollayer indicates that the version is Rel-14 to the first protocol layer,the terminal device may adopt, at the first protocol layer, the ratematching mechanism corresponding to Rel-14 to transmit the data; and ifthe second protocol layer indicates that the version is Rel-15 to thefirst protocol layer, the terminal device may adopt, at the firstprotocol layer, a TxD mechanism corresponding to Rel-15.

Alternatively, in the embodiment of the disclosure, the terminal devicemay send, at the second protocol layer, at least one of the followinginformation to the first protocol layer: the service identifier, the IPaddress, the service type, the service requirement, the bandinformation, the FQDN, the layer-2 address information, the PPPPinformation, or the PPPR information, and the method further includesthat: the terminal device determines, at the first protocol layer, theversion information of the data to be sent according to the at least oneof information, the version information being used for indicating theprotocol version for the service corresponding to the data to be sent.

That is, the terminal device may not determine the version informationat the second protocol layer, but send the service information exceptthe version information to the first protocol layer, and then determine,at the first protocol layer, the version information according to theservice information, so that the transmission mechanism corresponding tothe version information may be determined.

Alternatively, the network device or the server may configure a mappingrelationship between other service information and version informationin advance, or the mapping relationship may be pre-stored in theterminal device. The mapping relationship may also be set based on apreference of the terminal device.

Alternatively, in the embodiment of the disclosure, the method furtherincludes that: the terminal device determines, at the first protocollayer, a transmission carrier for the data to be sent according to amapping relationship between the transmission mechanism and thetransmission carrier.

Alternatively, in the embodiment of the disclosure, the method furtherincludes that: the terminal device determines, at a third protocollayer, the transmission carrier for the data to be sent according to themapping relationship between the transmission mechanism and thetransmission carrier, the third protocol layer being a layer below thefirst protocol layer.

Specifically, the service information may have a mapping relationshipwith the transmission mechanism and the transmission carrierrespectively. That is, the transmission carrier for the data to be sentor the transmission mechanism for the data to be sent may be determinedaccording to the service information of the data to be sent. Therefore,the transmission carrier has a corresponding mapping relationship withthe transmission mechanism. The terminal device, after determining thetransmission mechanism for the data to be sent, may further determinethe transmission carrier for the data to be sent according to themapping relationship between the transmission mechanism and thetransmission carrier. It is to be noted that the transmission carriermay be determined at the first protocol layer or the third protocollayer, i.e., a layer below the first protocol layer. There are no limitsmade thereto in the embodiment of the disclosure.

Alternatively, in the embodiment of the disclosure, the operation thatthe terminal device determines, at the first protocol layer, thetransmission mechanism for transmitting the data to be sent according tothe service information of the data to be sent includes that: theterminal device determines, at the first protocol layer, at least onetransmission mechanism for transmitting the data to be sent according tothe service information; and the method further includes that: theterminal device determines, at the first protocol layer, thetransmission mechanism for transmission of the data to be sent from theat least one transmission mechanism, according to the mappingrelationship between the transmission mechanism and the transmissioncarrier, and the transmission carrier for the data to be sent.

Alternatively, in the embodiment of the disclosure, the operation thatthe terminal device determines, at the first protocol layer, thetransmission mechanism for transmitting the data to be sent according tothe service information of the data to be sent includes that: theterminal device determines, at the first protocol layer, the at leastone transmission mechanism for transmitting the data to be sentaccording to the service information; and the method further includesthat: the terminal device determines, at the third protocol layer, thetransmission mechanism for transmission of the data to be sent in the atleast one transmission mechanism, according to a mapping relationshipbetween multiple transmission mechanisms and transmission carriers, andthe transmission carrier for the data to be sent, the third protocollayer being a layer below the first protocol layer.

Specifically, the terminal device may determine multiple availabletransmission mechanisms at first according to the service information ofthe data to be sent, and then the terminal device may further determinethe transmission mechanism finally for transmission of the data to besent according to the mapping relationship between the transmissionmechanism and the transmission carrier, and the transmission carrier forthe data to be sent. Similarly, the final transmission mechanism may bedetermined at the first protocol layer or may be determined at the thirdprotocol layer.

Therefore, according to the method for data transmission of theembodiment of the disclosure, the terminal device may send the data byuse of a more suitable transmission mechanism, and thus datatransmission performance is improved.

FIG. 4 is a schematic block diagram of a method 200 for datatransmission according to an embodiment of the disclosure. Asillustrated in FIG. 4, the method 200 is applied to an Internet ofvehicles system. The method 200 includes part or all of the followingcontents.

In S210, a terminal device acquires service information of data to besent.

In S220, the terminal device determines, from multiple transmissionpaths, a transmission path for transmitting the data to be sent,according to the service information.

It is to be noted that the service information of the data to be sent inthe embodiment is similar to the service information of the data to besent in the method 100, and both the first protocol layer and the secondprotocol layer are the same as those mentioned above. For simplicity,elaborations are omitted herein.

The Internet of vehicles system may include two types of datatransmission paths: one is a cellular path, i.e., a data transmissionpath between a network device and a terminal device in FIG. 2, and theother is an SL path, i.e., a direct connection path between a terminaldevice and a terminal device in FIG. 2. Correspondingly, there are twotypes of air interfaces: one is a Uu interface capable of implementingcommunication between a vehicle, an infrastructure and another vehiclein such a manner that a network device serves as a control center anddata is forwarded through the network device, and the other is a PC5interface capable of implementing direct data transmission betweenvehicles. The Internet of vehicles has two working scenarios: one is acellular network coverage-based scenario, in which the service may beprovided through the Uu interface of a cellular network, to implementhigh-bandwidth large-coverage communication, or the service may beprovided through the Pc5 interface to implement low-latencyhigh-reliability direct communication between a vehicle and an ambientnode; and the other is a working scenario independently of the cellularnetwork, in which the Internet of vehicles road service is providedthrough the PC5 interface in a region deployed with no networks, to meeta driving safety requirement. In the cellular network coverage-basedscenario, the Uu interface and the PC5 interface may be switchedflexibly and seamlessly for data transmission.

Alternatively, the Internet of vehicles system may include a cellularpath and at least one SL path, or may include multiple SL paths,different Radio Access Technologies (RATs) being adopted for themultiple SL paths, for example, an NR link, an LTE link or a WLAN link.That is, the terminal device may select, according to the serviceinformation, the transmission path from the cellular path and the SLpath, or select the transmission path from the multiple transmissionpaths. There are no limits made in the embodiment of the disclosure.

Alternatively, in the embodiment of the disclosure, a network device ora server may configure a mapping relationship between different serviceinformation and different transmission paths in advance. Or, the mappingrelationship may be pre-stored in the terminal device. For example,service type and transmission path are adopted. A voice service and avideo service may be mapped to the cellular path, and a short messagingservice may be mapped to the SL path. If the terminal device determinesthat a service type of the data to be sent is a voice service, thetransmission path available for the terminal device may be the cellularpath. If the terminal device determines that the service type of thedata to be sent is a short messaging service, the transmission pathavailable for the terminal device may be the SL path.

The transmission path may also be determined according to versioninformation. For example, the cellular path is adopted for a service ofRel-14, and the SL path is adopted for a service of Rel-15.

Alternatively, in the embodiment of the disclosure, the operation thatthe terminal device determines the transmission path for transmittingthe data to be sent from the multiple transmission paths according tothe service information includes that: the terminal device determines,at a first protocol layer, the transmission path for transmitting thedata to be sent from the multiple transmission paths according to theservice information and path configuration information, the pathconfiguration information being used for indicating a mappingrelationship between service information and a transmission path.

That is, the network device may configure the mapping relationshipbetween the transmission path and the service information, i.e., pathconfiguration information, in advance for the terminal device, and thenthe terminal device, after acquiring the service information of the datato be sent, may acquire, from the configuration information, thecorresponding transmission path. Furthermore, the terminal device maytransmit, at the first protocol layer, the data to be sent to a protocollayer of the determined transmission path. It is to be understood thatthe first protocol layer may be an application layer, access layer orsublayer of the access layer in V2X.

For example, a V2X layer may determine to send the data to be sent in anNR link according to a mapping relationship between a service identifierand a path, and then transmit the data to be sent to a physical protocollayer of NR, the data being sent according to a transmission mechanismof NR. For another example, the V2X layer may submit the data to be sentto a PDCP layer in the access layer, together with the pathconfiguration information for data submission, and the PDCP layer maydetermine to transmit the data to be sent to the physical protocol layerof NR according to the received path configuration information.

Therefore, according to the method for data transmission of theembodiment of the disclosure, the terminal device may send the data byuse of a more suitable transmission path, and thus data transmissionperformance is improved.

The method for data transmission according to the embodiments of thedisclosure is described above in detail and a data transmission deviceaccording to the embodiments of the disclosure will be described belowin combination with FIG. 5 to FIG. 8. The technical characteristicsdescribed in the method embodiments are applied to the following deviceembodiments.

FIG. 5 is a schematic block diagram of a terminal device 300 accordingto an embodiment of the disclosure. As illustrated in FIG. 5, theterminal device 300 is applied to an Internet of vehicles system. Theterminal device 300 includes a determination unit 310.

The determination unit 310 is configured to determine, at a firstprotocol layer, a transmission mechanism for transmitting data to besent, according to service information of the data to be sent.

Therefore, the terminal device in the embodiment of the disclosure maysend the data by use of a more suitable transmission mechanism, and thusdata transmission performance is improved.

Alternatively, in the embodiment of the disclosure, the serviceinformation includes at least one of the following information: aservice identifier, an IP address, a service type, a servicerequirement, band information, version information, an FQDN, layer-2address information, PPPP information, or PPPR information.

Alternatively, in the embodiment of the disclosure, the terminal devicefurther includes an acquisition unit and a sending unit.

The acquisition unit is configured to acquire at a second protocol layerthe service information of the data to be sent.

The sending unit is configured to send at the second protocol layer theservice information to the first protocol layer.

Alternatively, in the embodiment of the disclosure, if the serviceinformation is the version information, the acquisition unit isspecifically configured to determine, at the second protocol layer, theversion information of the data to be sent, according to at least onepiece of information of the following information: the serviceidentifier, the IP address, the service type, the service requirement,the band information, the FQDN, the layer-2 address information, thePPPP information, or the PPPR information, the version information beingused for indicating a protocol version for a service corresponding tothe data to be sent.

Alternatively, in the embodiment of the disclosure, if the serviceinformation is at least one piece of information of the followinginformation: the service identifier, the IP address, the service type,the service requirement, the band information, the FQDN, the layer-2address information, the PPPP information, or the PPPR information, thedetermination unit is further configured to:

determine, at the first protocol layer, the version information of thedata to be sent, according to the at least one piece of information, theversion information being used for indicating the protocol version forthe service corresponding to the data to be sent.

Alternatively, in the embodiment of the disclosure, the determinationunit is specifically configured to:

determine the version information of the data to be sent according tothe at least one piece of information and a mapping relationship betweenat least one piece of information and version information.

Alternatively, in the embodiment of the disclosure, the mappingrelationship is pre-stored in the terminal device, or is configured by anetwork device, or is configured by a server.

Alternatively, in the embodiment of the disclosure, the transmissionmechanism includes at least one of a digital modulation mechanism, arate matching mechanism, a duplicate transmission mechanism, or a TxD.

Alternatively, in the embodiment of the disclosure, the digitalmodulation mechanism includes one of BPSK, QPSK, 16QAM, 64QAM and256QAM.

Alternatively, in the embodiment of the disclosure, the first protocollayer is an access layer, and the second protocol layer is anapplication layer.

Alternatively, in the embodiment of the disclosure, the IP address is anIP address of the server.

Alternatively, in the embodiment of the disclosure, the determinationunit is further configured to determine, at the first protocol layer, atransmission carrier for the data to be sent, according to a mappingrelationship between a transmission mechanism and a transmissioncarrier.

Alternatively, in the embodiment of the disclosure, the determinationunit is specifically configured to determine, at the first protocollayer, at least one transmission mechanism for transmitting the data tobe sent, according to the service information; and the determinationunit is further configured to determine, at the first protocol layer,the transmission mechanism for transmission of the data to be sent, fromthe at least one transmission mechanism, according to a mappingrelationship between at least one transmission mechanism and atransmission carrier, and the transmission carrier for the data to besent.

Alternatively, in the embodiment of the disclosure, the determinationunit is further configured to determine, at a third protocol layer, thetransmission carrier for the data to be sent, according to the mappingrelationship between the transmission mechanism and the transmissioncarrier, the third protocol layer being a layer below the first protocollayer.

Alternatively, in the embodiment of the disclosure, the determinationunit is specifically configured to determine, at the first protocollayer, the at least one transmission mechanism for transmitting the datato be sent according to the service information; and the determinationunit is further configured to determine, at the third protocol layer,the transmission mechanism for transmission of the data to be sent, fromthe at least one transmission mechanism, according to the mappingrelationship between the at least one transmission mechanism and thetransmission carrier and the transmission carrier for the data to besent, the third protocol layer being a layer below the first protocollayer.

It is to be understood that the terminal device 300 according to theembodiment of the disclosure may correspond to the terminal device inthe method embodiment of the disclosure and the abovementioned and otheroperations and/or functions of each unit in the terminal device 300 areadopted to implement the corresponding flows executed by the terminaldevice in the method in FIG. 3 respectively and will not be elaboratedherein for simplicity.

FIG. 6 is a schematic block diagram of a terminal device 400 accordingto an embodiment of the disclosure. As illustrated in FIG. 6, theterminal device 400 is applied to an Internet of vehicles system. Theterminal device 400 includes an acquisition unit 410 and a determinationunit 420.

The acquisition unit 410 is configured to acquire service information ofdata to be sent.

The determination unit 420 is configured to determine a transmissionpath for transmitting the data to be sent, from multiple transmissionpaths, according to the service information.

Therefore, the terminal device in the embodiment of the disclosure maysend the data by use of a more suitable transmission path, and thus datatransmission performance is improved.

Alternatively, in the embodiment of the disclosure, the multipletransmission paths include a cellular path and at least one SL path, theSL path being a D2D path between two terminal devices.

Alternatively, in the embodiment of the disclosure, the multiple SLpaths include at least two of an NR link, an LTE link, and a WLAN link.

Alternatively, in the embodiment of the disclosure, the serviceinformation includes at least one piece of information of the followinginformation: a service identifier, an IP address, a service type, aservice requirement, band information, version information, an FQDN,layer-2 address information, PPPP information, or PPPR information.

Alternatively, in the embodiment of the disclosure, the determinationunit is specifically configured to determine, at a first protocol layer,the transmission path for transmitting the data to be sent, from themultiple transmission paths, according to the service information andpath configuration information, the path configuration information beingused for indicating a mapping relationship between service informationand a transmission path.

Alternatively, in the embodiment of the disclosure, the serviceinformation and/or the path configuration information are/is configuredthrough a network or pre-stored in the first protocol layer.

Alternatively, in the embodiment of the disclosure, the terminal devicefurther includes a transmission unit, configured to transmit the data tobe sent to a protocol layer of the transmission path determined by thedetermination unit at the first protocol layer.

Alternatively, in the embodiment of the disclosure, the first protocollayer is an application layer, an access layer or a sublayer of theaccess layer.

It is to be understood that the terminal device 400 according to theembodiment of the disclosure may correspond to the terminal device inthe method embodiment of the disclosure and the abovementioned and otheroperations and/or functions of each unit in the terminal device 400 areadopted to implement the corresponding flows executed by the terminaldevice in the method in FIG. 4 respectively and will not be elaboratedherein for simplicity.

As illustrated in FIG. 7, an embodiment of the disclosure also providesa terminal device 500. The terminal device 500 may be the terminaldevice 300 in FIG. 5, and may be configured to execute contents of theterminal device corresponding to the method 100 in FIG. 3. The terminaldevice 500 includes an input interface 510, an output interface 520, aprocessor 530 and a memory 540. The input interface 510, the outputinterface 520, the processor 530 and the memory 540 may be connectedthrough a bus system. The memory 540 is configured to store a program,instructions or codes. The processor 530 is configured to execute theprogram instructions or codes in the memory 540 to control the inputinterface 510 to receive a signal, control the output interface 520 tosend a signal and complete operations in the method embodiment.

Therefore, the terminal device of the embodiment of the disclosure maysend the data by use of a more suitable transmission mechanism, and thusdata transmission performance is improved.

It is to be understood that, in the embodiment of the disclosure, theprocessor 530 may be a Central Processing Unit (CPU), or the processor530 may be another universal processor, a Digital Signal Processor(DSP), an Application Specific Integrated Circuit (ASIC), a FieldProgrammable Gate Array (FPGA) or another programmable logic device,discrete gate or transistor logic device and discrete hardware componentand the like. The universal processor may be a microprocessor or theprocessor may also be any conventional processor and the like.

The memory 540 may include a Read-Only Memory (ROM) and a Random AccessMemory (RAM), and provides instructions and data for the processor 530.A part of the memory 540 may further include a nonvolatile RAM. Forexample, the memory 540 may further store information of a device type.

In an implementation process, each content of the method may becompleted by an integrated logic circuit of hardware in the processor530 or instructions in a software form. The contents of the methoddisclosed in combination with the embodiments of the disclosure may bedirectly embodied to be executed and completed by a hardware processoror executed and completed by a combination of hardware and softwaremodules in the processor. The software module may be located in a maturestorage medium in this field such as a RAM, a flash memory, a ROM, aprogrammable ROM or electrically erasable programmable ROM and aregister. The storage medium is located in the memory 540. The processor530 reads information in the memory 540 and completes the contents ofthe method in combination with hardware. No more detailed descriptionswill be made herein to avoid repetitions.

In a specific implementation mode, the sending unit in the terminaldevice 300 may be implemented by the output interface 520 in FIG. 7, andthe acquisition unit and determination unit in the terminal device 300may be implemented by the processor 530 in FIG. 7.

As illustrated in FIG. 8, an embodiment of the disclosure also providesa terminal device 600. The terminal device 600 may be the terminaldevice 400 in FIG. 6, and may be configured to execute contents of theterminal device corresponding to the method 200 in FIG. 4. The terminaldevice 600 includes an input interface 610, an output interface 620, aprocessor 630 and a memory 640. The input interface 610, the outputinterface 620, the processor 630 and the memory 640 may be connectedthrough a bus system. The memory 640 is configured to store a program,instructions or a code. The processor 630 is configured to execute theprogram instructions or code in the memory 640 to control the inputinterface 610 to receive a signal, control the output interface 620 tosend a signal and complete operations in the method embodiment.

Therefore, the terminal device of the embodiment of the disclosure maysend the data by use of a more suitable transmission path, and thus datatransmission performance is improved.

It is to be understood that, in the embodiment of the disclosure, theprocessor 630 may be a CPU and the processor 630 may also be anotheruniversal processor, a DSP, an ASIC, an FPGA or another programmablelogic device, discrete gate or transistor logic device and discretehardware component and the like. The universal processor may be amicroprocessor or the processor may also be any conventional processorand the like.

The memory 640 may include a ROM and a RAM and provides instructions anddata for the processor 630. A part of the memory 640 may further includea nonvolatile RAM. For example, the memory 640 may further storeinformation of a device type.

In an implementation process, each content of the method may becompleted by an integrated logic circuit of hardware in the processor630 or instructions in a software form. The contents of the methoddisclosed in combination with the embodiments of the disclosure may bedirectly embodied to be executed and completed by a hardware processoror executed and completed by a combination of hardware and softwaremodules in the processor. The software module may be located in a maturestorage medium in this field such as a RAM, a flash memory, a ROM, aProgrammable ROM (PROM) or Electrically Erasable PROM (EEPROM) and aregister. The storage medium is located in the memory 640. The processor630 reads information in the memory 640 and completes the contents ofthe method in combination with hardware. No more detailed descriptionswill be made herein to avoid repetitions.

In a specific implementation mode, the acquisition unit anddetermination unit in the terminal device 400 may be implemented by theprocessor 630 in FIG. 6.

FIG. 9 is a schematic block diagram of a method for data transmission700 according to an embodiment of the disclosure. As illustrated in FIG.9, the method 700 is applied to an Internet of vehicles system. Themethod 700 includes part or all of the following contents.

In S710, a terminal device determines, at a first protocol layer, atransmission mechanism for transmitting data to be sent on a firsttransmission resource according to configuration information, and/orselects, at a first protocol layer, a transmission resource for the datato be sent, according to configuration information.

Specifically, a network device may configure selectable transmissionmechanisms corresponding to different transmission resources for theterminal device. For example, the network device may configure a mappingrelationship illustrated in Table 1 for the terminal device. It is to beunderstood that the transmission mechanism is the same as that describedabove. For simplicity, elaborations are omitted herein.

TABLE 1 Transmission resource 1 Transmission mechanism 1, transmissionmechanism 2 and transmission mechanism 3 Transmission resource 2Transmission mechanism 2 and transmission mechanism 4 Transmissionresource 3 Transmission mechanism 3 and transmission mechanism 4Transmission resource 4 Transmission mechanism 2, transmission mechanism3 and transmission mechanism 4

If the terminal device selects to transmit the data to be sent on thetransmission resource 1 in Table 1, the terminal device may determinethe transmission mechanisms, including the transmission mechanism 1, thetransmission mechanism 2 and the transmission mechanism 3, correspondingto the transmission resource 1 according to the configurationinformation, i.e., Table 1. The terminal device may select anytransmission mechanism therein to transmit the data to be sent, and theterminal device may also select a transmission mechanism thereinaccording to a certain rule to transmit the data to be sent. How theterminal device selects the transmission mechanism according to theconfiguration information is not limited in the embodiment of thedisclosure.

Or, if the terminal device selects to transmit the data to be sent byuse of the transmission mechanism 2 in Table 1, the terminal device maydetermine the transmission resources, including the transmissionresource 1, the transmission resource 2 and the transmission resource 4,corresponding to the transmission mechanism 2 according to theconfiguration information, i.e., Table 2. The terminal device may selectany transmission resource therein to transmit the data to be sent, andthe terminal device may also select a transmission resource thereinaccording to a certain rule to transmit the data to be sent. How theterminal device selects the transmission resource according to theconfiguration information is not limited in the embodiment of thedisclosure.

Therefore, according to the method for data transmission of theembodiment of the disclosure, the transmission resource and/ortransmission mechanism are/is determined according to the configurationinformation of the transmission resource and the transmission mechanism,which is favorable for improving data transmission performance of theInternet of vehicles system.

Alternatively, in the embodiment of the disclosure, the terminal devicereceives first indication information, the first indication informationbeing used for indicating a first transmission mechanism in the at leastone transmission mechanism; and the operation that the terminal devicedetermines the transmission mechanism for transmitting the data to besent on the first transmission resource according to the configurationinformation includes that: the terminal device determines the firsttransmission mechanism to be the transmission mechanism for transmittingthe data to be sent on the first transmission resource according to theconfiguration information and the first indication information.

For example, for the transmission resource 1 in Table 1, the selectabletransmission mechanisms are the transmission mechanism 1, thetransmission mechanism 2 and the transmission mechanism 3 respectively,and the network device may further make configurations for the terminaldevice as follows: the transmission mechanism 1 corresponds to 00, thetransmission mechanism 2 corresponds to 01 and the transmissionmechanism 3 corresponds to 10. The network device may send indicationinformation to the terminal device. For example, if the indicationinformation is 10, the terminal device may determine the transmissionmechanism 3 indicated by the indication information from multipletransmission mechanisms indicated by the configuration information, tobe the transmission mechanism for transmitting the data to be sent.

Alternatively, in the embodiment of the disclosure, the method furtherincludes that: the terminal device receives first indicationinformation, the first indication information being used for indicatingat least one transmission mechanism for transmitting the data to besent; and the operation that the terminal device determines thetransmission mechanism for transmitting the data to be sent on the firsttransmission resource according to the configuration informationincludes that: the terminal device determines the transmission mechanismfor transmitting the data to be sent on the first transmission resourcefrom an intersection of at least one transmission mechanism indicated bythe configuration information and the at least one transmissionmechanism indicated by the first indication information.

For example, if the terminal device selects to transmit the data to besent on the transmission resource 1, it may be obtained according toTable 1, i.e., the configuration information, that the alternativetransmission mechanisms on the transmission resource include thetransmission mechanism 1, the transmission mechanism 2 and thetransmission mechanism 3. If the indication information received by theterminal device indicates that the transmission mechanism fortransmitting the data to be sent includes the transmission mechanism 3and the transmission mechanism 4, the terminal device may acquire anintersection (i.e., the transmission mechanism 3) of the transmissionmechanism 1, transmission mechanism 2 and transmission mechanism 3indicated by the configuration information and the transmissionmechanism 3 and transmission mechanism 4 indicated by the indicationinformation, and the terminal device may further determine thetransmission mechanism 3 to be the transmission mechanism fortransmitting the data to be sent. It is to be understood thatdescriptions are made herein with the condition that the intersectionincludes only one transmission mechanism as an example, and when theintersection of the transmission mechanisms indicated by theconfiguration information and indicated by the indication informationincludes multiple transmission mechanisms, the terminal device mayselect any transmission mechanism from the intersection, or the terminaldevice may also select a transmission mechanism from the intersectionaccording to a certain rule.

Alternatively, in the embodiment of the disclosure, the configurationinformation is used for indicating a mapping relationship between atransmission resource and a transmission mechanism, and the methodfurther includes that: the terminal device receives second indicationinformation, the second indication information being used for indicatinga second transmission mechanism in the mapping relationship; and theoperation that the terminal device selects the transmission resource forthe data to be sent according to the configuration information includesthat: the terminal device determines a transmission resourcecorresponding to the second transmission mechanism in the mappingrelationship, to be the transmission resource for the data to be sent.

For example, if the indication information received by the terminaldevice indicates the transmission mechanism 2 in Table 1, the terminaldevice may determine according to the mapping relationship indicated byTable 1, i.e., the configuration information, that the transmissionresource corresponding to the transmission mechanism 2 includes thetransmission resource 1, the transmission resource 2 and thetransmission resource 4, and the terminal device may select anytransmission resource therein to transmit the data to be sent, or mayselect a transmission resource to transmit the data to be sent accordingto a certain rule.

Alternatively, in the embodiment of the disclosure, the configurationinformation is used for indicating the mapping relationship between thetransmission resource and the transmission mechanism, and the methodfurther includes that: the terminal device receives the secondindication information, the second indication information being used forindicating the transmission mechanism for transmitting the data to besent; and the operation that the terminal device selects thetransmission resource for the data to be sent according to theconfiguration information includes that: when a transmission mechanismcorresponding to a presently adopted transmission resource in theconfiguration information conflicts with the transmission mechanismindicated by the second indication information, the terminal devicedetermines a transmission resource corresponding to the transmissionmechanism indicated by the second indication information, to be thetransmission resource for the data to be sent.

Specifically, the terminal device may continue transmitting the data tobe sent on a transmission resource for sending data last time, and theterminal device may determine whether a transmission mechanism indicatedby the configuration information and corresponding to the transmissionresource adopted last time conflicts with the transmission mechanismindicated by the indication information or not at first, if NO,continues adopting the transmission resource adopted last time and, ifYES, performs resource reselection. For example, if the transmissionresource adopted last time is the transmission resource 1 in Table 1,the transmission mechanism corresponding to the transmission resource 1in Table 1 includes the transmission mechanism 1, the transmissionmechanism 2 and the transmission mechanism 3. If the indicationinformation indicates the transmission mechanism 4, the terminal devicemay select any transmission resource from the transmission resource 2,transmission resource 3 and transmission resource 4 corresponding to thetransmission mechanism 4 in Table 1 to transmit the data to be sent, ormay select a transmission resource therein according to a certain ruleto transmit the data to be sent.

Alternatively, in the embodiment of the disclosure, selection of thetransmission resource may be resource pool selection and/or resourcepool reselection, or selection of the transmission resource may becarrier selection and/or carrier reselection.

Alternatively, in the embodiment of the disclosure, the terminal devicemay also determine the transmission mechanism for transmitting the datato be sent and/or select the transmission resource for the data to besent based on the service information, the configuration informationand/or various indication information. It is to be understood that theservice information mentioned here is the same as that described aboveand will not be elaborated herein.

The method for data transmission according to the embodiments of thedisclosure is described above in detail and a data transmission deviceaccording to the embodiments of the disclosure will be described belowin combination with FIG. 10 to FIG. 11. The technical characteristicsdescribed in the method embodiments are applied to the following deviceembodiments.

FIG. 10 is a schematic block diagram of a terminal device 800 accordingto an embodiment of the disclosure. As illustrated in FIG. 10, theterminal device 800 is applied to an Internet of vehicles system. Theterminal device 800 includes a determination unit 810.

The determination unit 810 is configured to determine a transmissionmechanism for transmitting data to be sent on a first transmissionresource according to configuration information and/or select atransmission resource for the data to be sent according to configurationinformation.

Therefore, the terminal device of the embodiment of the disclosuredetermines the corresponding transmission resource and/or transmissionmechanism according to the configuration information, which is favorablefor improving data transmission performance of the Internet of vehiclessystem.

Alternatively, in the embodiment of the disclosure, the configurationinformation is used for indicating at least one selectable transmissionmechanism on the first transmission resource.

Alternatively, in the embodiment of the disclosure, the terminal devicefurther includes a first receiving unit, configured to receive firstindication information, the first indication information being used forindicating a first transmission mechanism in the at least onetransmission mechanism.

The determination unit is specifically configured to determine the firsttransmission mechanism to be the transmission mechanism for transmittingthe data to be sent on the first transmission resource, according to theconfiguration information and the first indication information.

Alternatively, in the embodiment of the disclosure, the terminal devicefurther includes the first receiving unit, configured to receive thefirst indication information, the first indication information beingused for indicating at least one transmission mechanism for transmittingthe data to be sent; and the determination unit is specificallyconfigured to determine the transmission mechanism for transmitting thedata to be sent on the first transmission resource, from an intersectionof the at least one transmission mechanism indicated by theconfiguration information and the at least one transmission mechanismindicated by the first indication information.

Alternatively, in the embodiment of the disclosure, the configurationinformation is used for indicating a mapping relationship between atransmission resource and a transmission mechanism.

Alternatively, in the embodiment of the disclosure, the terminal devicefurther includes a second receiving unit, configured to receive secondindication information, the second indication information being used forindicating a second transmission mechanism in the mapping relationship;and the determination unit is specifically configured to determine atransmission resource corresponding to the second transmission mechanismin the mapping relationship to be the transmission resource for the datato be sent.

Alternatively, in the embodiment of the disclosure, the terminal devicefurther includes the second receiving unit, configured to receive thesecond indication information, the second indication information beingused for indicating the transmission mechanism for transmitting the datato be sent; and the determination unit is specifically configured to,when a transmission mechanism corresponding to a presently adoptedtransmission resource in the configuration information conflicts withthe transmission mechanism indicated by the second indicationinformation, determine a transmission resource corresponding to thetransmission mechanism indicated by the second indication information tobe the transmission resource for the data to be sent.

Alternatively, in the embodiment of the disclosure, selection of thetransmission resource includes carrier selection and/or carrierreselection.

Alternatively, in the embodiment of the disclosure, selection of thetransmission resource includes resource pool selection and/or resourcepool reselection.

It is to be understood that the terminal device 800 according to theembodiment of the disclosure may correspond to the terminal device inthe method embodiment of the disclosure and the abovementioned and otheroperations and/or functions of each unit in the terminal device 800 areadopted to implement the corresponding flows executed by the terminaldevice in the method in FIG. 9 respectively and will not be elaboratedherein for simplicity.

As illustrated in FIG. 11, an embodiment of the disclosure also providesa terminal device 900. The terminal device 900 may be the terminaldevice 800 in FIG. 10, and may be configured to execute contents of theterminal device corresponding to the method 700 in FIG. 9. The terminaldevice 900 illustrated in FIG. 11 includes a processor 910, and theprocessor 910 may call and run a computer program in a memory toimplement the method in the embodiment of the disclosure.

Therefore, the terminal device of the embodiment of the disclosuredetermines the corresponding transmission resource and/or transmissionmechanism according to the configuration information, which is favorablefor improving data transmission performance of the Internet of vehiclessystem.

Alternatively, as illustrated in FIG. 11, the terminal device 900 mayfurther include the memory 920. The processor 910 may call and run thecomputer program in the memory 920 to implement the method in theembodiment of the disclosure.

The memory 920 may be an independent device independent of the processor910 and may also be integrated into the processor 910.

Alternatively, as illustrated in FIG. 11, the terminal device 900 mayfurther include a transceiver 930, and the processor 910 may control thetransceiver 930 to communicate with another device, specifically sendinginformation or data to the other device or receiving information or datasent by the other device.

The transceiver 930 may include a transmitter and a receiver. Thetransceiver 930 may further include antennae, and the number of theantennae may be one or more.

Alternatively, the terminal device 900 may be a terminal device of theembodiment of the disclosure, and the terminal device 900 may implementcorresponding flows implemented by the terminal device in each method ofthe embodiments of the disclosure. For simplicity, elaborations areomitted herein.

In a specific implementation mode, the first receiving unit and secondreceiving unit in the terminal device 800 may be implemented by thetransceiver 930 in FIG. 11, and the acquisition unit in the terminaldevice 800 may be implemented by the processor 910 in FIG. 11.

FIG. 12 is a schematic block diagram of a chip 1000 according to anembodiment of the disclosure. The chip 1000 illustrated in FIG. 12includes a processor 1010, and the processor 1010 may call and run acomputer program in a memory to implement the method 100 in theembodiment of the disclosure.

Alternatively, as illustrated in FIG. 12, the chip 1000 may furtherinclude the memory 1020. The processor 1010 may call and run thecomputer program in the memory 1020 to implement the method in theembodiment of the disclosure.

The memory 1020 may be an independent device independent of theprocessor 1010 and may also be integrated into the processor 1010.

Alternatively, the chip 1000 may further include an input interface1030. The processor 1010 may control the input interface 1030 tocommunicate with another device or chip, specifically acquiringinformation or data sent by the other device or chip.

Alternatively, the chip 1000 may further include an output interface1040. The processor 1010 may control the output interface 1040 tocommunicate with the other device or chip, specifically outputtinginformation or data sent by the other device or chip.

Alternatively, the chip may be applied to the terminal device of theembodiment of the disclosure, and the chip may implement correspondingflows implemented by the terminal device in the method 100 of theembodiment of the disclosure. For simplicity, elaborations are omittedherein.

It is to be understood that the chip mentioned in the embodiment of thedisclosure may also be called a system-level chip, a system chip, a chipsystem or a system on chip, etc.

FIG. 13 is a schematic block diagram of a chip 2000 according to anembodiment of the disclosure. The chip 2000 illustrated in FIG. 13includes a processor 2010, and the processor 2010 may call and run acomputer program in a memory to implement the method 200 in theembodiment of the disclosure.

Alternatively, as illustrated in FIG. 13, the chip 2000 may furtherinclude the memory 2020. The processor 2010 may call and run thecomputer program in the memory 2020 to implement the method in theembodiment of the disclosure.

The memory 2020 may be an independent device independent of theprocessor 2010 and may also be integrated into the processor 2010.

Alternatively, the chip 2000 may further include an input interface2030. The processor 2010 may control the input interface 2030 tocommunicate with another device or chip, specifically acquiringinformation or data sent by the other device or chip.

Alternatively, the chip 2000 may further include an output interface2040. The processor 2010 may control the output interface 2040 tocommunicate with the other device or chip, specifically outputtinginformation or data sent by the other device or chip.

Alternatively, the chip may be applied to the terminal device of theembodiment of the disclosure, and the chip may implement correspondingflows implemented by the terminal device in the method 200 of theembodiment of the disclosure. For simplicity, elaborations are omittedherein.

It is to be understood that the chip mentioned in the embodiment of thedisclosure may also be called a system-level chip, a system chip, a chipsystem or a system on chip, etc.

FIG. 14 is a schematic block diagram of a chip 3000 according to anembodiment of the disclosure. The chip 3000 illustrated in FIG. 14includes a processor 3010, and the processor 3010 may call and run acomputer program in a memory to implement the method 700 in theembodiment of the disclosure.

Alternatively, as illustrated in FIG. 14, the chip 3000 may furtherinclude the memory 3020. The processor 3010 may call and run thecomputer program in the memory 3020 to implement the method in theembodiment of the disclosure.

The memory 3020 may be an independent device independent of theprocessor 3010 and may also be integrated into the processor 3010.

Alternatively, the chip 3000 may further include an input interface3030. The processor 3010 may control the input interface 3030 tocommunicate with another device or chip, specifically acquiringinformation or data sent by the other device or chip.

Alternatively, the chip 3000 may further include an output interface3040. The processor 3010 may control the output interface 3040 tocommunicate with the other device or chip, specifically outputtinginformation or data sent by the other device or chip.

Alternatively, the chip may be applied to the terminal device of theembodiment of the disclosure, and the chip may implement correspondingflows implemented by the terminal device in the method 700 of theembodiment of the disclosure. For simplicity, elaborations are omittedherein.

It is to be understood that the chip mentioned in the embodiment of thedisclosure may also be called a system-level chip, a system chip, a chipsystem or a system on chip, etc.

The processor mentioned above may be a universal processor, a DSP, anASIC, an FPGA or another programmable logical device, transistor logicaldevice and discrete hardware component, etc. The universal processormentioned above may be a microprocessor or may also be any conventionalprocessor and the like.

The memory mentioned above may be a volatile memory or a nonvolatilememory, or may also include both the volatile and nonvolatile memories.The nonvolatile memory may be a ROM, a PROM, an Erasable PROM (EPROM),an EEPROM or a flash memory. The volatile memory may be a RAM.

It is to be understood that the memory is exemplarily but unlimitedlydescribed. For example, the memory in the embodiments of the disclosuremay also be a Static RAM (SRAM), a Dynamic RAM (DRAM), a SynchronousDRAM (SDRAM), a Double Data Rate SDRAM (DDRSDRAM), an Enhanced SDRAM(ESDRAM), a Synchlink DRAM (SLDRAM) and a Direct Rambus RAM (DR RAM).That is, the memory in the embodiments of the disclosure is intended toinclude, but not limited to, memories of these and any other propertypes.

Those of ordinary skill in the art may realize that the units andalgorithm steps of each example described in combination with theembodiments disclosed in the disclosure may be implemented by electronichardware or a combination of computer software and the electronichardware. Whether these functions are executed in a hardware or softwaremanner depends on specific applications and design constraints of thetechnical solutions. Professionals may realize the described functionsfor each specific application by use of different methods, but suchrealization shall fall within the scope of the disclosure.

Those skilled in the art may clearly learn about that specific workingprocesses of the system, device and unit described above may refer tothe corresponding processes in the method embodiment and will not beelaborated herein for convenient and brief description.

In some embodiments provided by the disclosure, it is to be understoodthat the disclosed system, device and method may be implemented inanother manner. For example, the device embodiment described above isonly schematic, and for example, division of the units is only logicfunction division, and other division manners may be adopted duringpractical implementation. For example, multiple units or components maybe combined or integrated into another system, or some characteristicsmay be neglected or not executed. In addition, coupling or directcoupling or communication connection between each displayed or discussedcomponent may be indirect coupling or communication connection,implemented through some interfaces, of the device or the units, and maybe electrical and mechanical or adopt other forms.

The units described as separate parts may or may not be physicallyseparated, and parts displayed as units may or may not be physicalunits, and namely may be located in the same place, or may also bedistributed to multiple network units. Part or all of the units may beselected to achieve the purpose of the solutions of the embodimentsaccording to a practical requirement.

In addition, each functional unit in each embodiment of the disclosuremay be integrated into a processing unit, each unit may also physicallyexist independently, and two or more than two units may also beintegrated into a unit.

When being realized in form of software functional unit and sold or usedas an independent product, the function may also be stored in acomputer-readable storage medium. Based on such an understanding, thetechnical solutions of the disclosure substantially or parts makingcontributions to the conventional art or part of the technical solutionsmay be embodied in form of software product, and the computer softwareproduct is stored in a storage medium, including a plurality ofinstructions configured to enable a computer device (which may be apersonal computer, a server, a network device or the like) to executeall or part of the steps of each embodiment of the disclosure. Thestorage medium includes: various media capable of storing program codessuch as a U disk, a mobile hard disk, a ROM, a RAM, a magnetic disk oran optical disk.

The above is only the specific implementation mode of the disclosure andnot intended to limit the scope of protection of the disclosure. Anyvariations or replacements apparent to those skilled in the art withinthe technical scope disclosed by the disclosure shall fall within thescope of protection of the disclosure. Therefore, the scope ofprotection of the disclosure shall be subject to the scope of protectionof the claims.

1. A method for data transmission, applied to an Internet of vehiclessystem, and comprising: acquiring, by a terminal device, versioninformation of data to be sent; and determining, by the terminal device,a digital modulation mechanism for transmitting the data to be sent,according to the version information of the data to be sent, wherein,acquiring, by the terminal device, the version information of the datato be sent comprises: determining, by the terminal device, the versioninformation of the data to be sent according to at least one piece ofinformation of the following information: a service identifier, aninternet protocol (IP) address, a service type, a service requirement, afully qualified domain name (FQDN), layer-2 address information,proximity-based service (ProSe) per-packet priority (PPPP) information,or ProSe per-packet reliability (PPPR) information, wherein the versioninformation is used for indicating a protocol version for a servicecorresponding to the data to be sent.
 2. The method of claim 1, whereindetermining, by the terminal device, the version information of the datato be sent according to the at least one piece of information comprises:determining, by the terminal device, the version information of the datato be sent, according to the at least one piece of information and amapping relationship between the at least one piece of information andthe version information.
 3. The method of claim 2, wherein the mappingrelationship between the at least one piece of information and theversion information is pre-stored in the terminal device, or isconfigured by a network device, or is configured by a server.
 4. Themethod of claim 1, wherein the protocol version for the servicecorresponding to the data to be sent comprises at least one of: aprotocol version of 3rd Generation Partnership Project (3GPP) Release-14(Rel-14), or a protocol version of Rel-15.
 5. The method of claim 1,wherein determining, by the terminal device, the digital modulationmechanism for transmitting the data to be sent, according to the versioninformation of the data to be sent comprises: determining, by theterminal device, the digital modulation mechanism for transmitting thedata to be sent, according to the protocol version for the serviceindicated by the version information.
 6. The method of claim 4, whereindetermining, by the terminal device, the digital modulation mechanismfor transmitting the data to be sent, according to the versioninformation of the data to be sent comprises: determining, by theterminal device, the digital modulation mechanism for transmitting thedata to be sent, according to the protocol version for the serviceindicated by the version information.
 7. The method of claim 1, whereinthe digital modulation mechanism comprises one of binary phase shiftingkeying (BPSK), quadrature phase shifting keying (QPSK), 16 quadratureamplitude modulation (QAM), 64QAM and 256QAM.
 8. A terminal device,comprising: a processor, configured to: acquire version information ofdata to be sent; and determine a digital modulation mechanism fortransmitting the data to be sent, according to the version informationof the data to be sent, wherein the processor is configured to:determine the version information of the data to be sent according to atleast one piece of information of the following information: a serviceidentifier, an internet protocol (IP) address, a service type, a servicerequirement, a fully qualified domain name (FQDN), layer-2 addressinformation, proximity-based service (ProSe) per-packet priority (PPPP)information, or ProSe per-packet reliability (PPPR) information, whereinthe version information is used for indicating a protocol version for aservice corresponding to the data to be sent.
 9. The terminal device ofclaim 8, wherein the processor is configured to: determine the versioninformation of the data to be sent, according to the at least one pieceof information and a mapping relationship between the at least one pieceof information and the version information.
 10. The terminal device ofclaim 9, wherein the mapping relationship between the at least one pieceof information and the version information is pre-stored in the terminaldevice, or is configured by a network device, or is configured by aserver.
 11. The terminal device of claim 8, wherein the protocol versionfor the service corresponding to the data to be sent comprises at leastone of: a protocol version of 3rd Generation Partnership Project (3GPP)Release-14 (Rel-14), or a protocol version of Rel-15.
 12. The terminaldevice of claim 8, wherein the processor is configured to: determine thedigital modulation mechanism for transmitting the data to be sent,according to the protocol version for the service indicated by theversion information.
 13. The terminal device of claim 11, wherein theprocessor is configured to: determine the digital modulation mechanismfor transmitting the data to be sent, according to the protocol versionfor the service indicated by the version information.
 14. The terminaldevice of claim 8, wherein the digital modulation mechanism comprisesone of binary phase shifting keying (BPSK), quadrature phase shiftingkeying (QPSK), 16 quadrature amplitude modulation (QAM), 64QAM and256QAM.